[B! aws] labochoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

labocho id:labocho

awsã«é–¢ã™ã‚‹labochoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (12)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

SNI ãŒã¾ã ãã“ã¾ã§ãƒãƒ”ãƒ¥ãƒ©ãƒ¼ã§ã¯ãªã„ã®ã§ã‚µãƒ¼ãƒè¨¼æ˜Žæ›¸ã‚’æ‰±ã†ã«ã¯ 1 æžšã« 1 ã¤ã® IP address ãŒè¦ã‚‹ã®ã§ãŠå›°ã‚Šã®ãã“ã®ã‚ãªãŸ!! - ã—ã¦ã¿ã‚“ã¨ã¦
å¤ã„è©±ã«ãªã‚Šã¾ã™ãŒã€AWS ã§ã¯ VPC å†…ã® EC2 ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã®ã‚¤ãƒ³ã‚¿ãƒ¼ãƒ•ã‚§ãƒ¼ã‚¹ã«è¤‡æ•°ã® IP address ã‚’å‰²ã‚Šå½“ã¦ã‚‹ã“ã¨ãŒã§ãã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã—ãŸ http://aws.typepad.com/aws_japan/2012/07/multiple-ip-addresses-for-ec2-instances-in-a-virtual-private-cloud.html å˜ä¸€ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã§è¤‡æ•°ã®SSLã‚µã‚¤ãƒˆã‚’ãƒ›ã‚¹ãƒˆ ç•°ãªã‚‹IPã‚¢ãƒ‰ãƒ¬ã‚¹ã«ãã‚Œãžã‚Œçµã³ã¤ã‘ã‚‹ã“ã¨ã§ã€å˜ä¸€ã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«è¤‡æ•°ã®SSLè¨¼æ˜Žæ›¸ã‚’ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã§ãã‚‹ã‚ˆã†ã«ãªã‚Šã¾ã™ã€‚ ã¾ã˜ã§ãƒ¼ã€‚è©¦ãã†ã€è©¦ã—ã¾ã—ã‚‡ã†ã€‚ http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/instance-types.html#AvailableIpPerENI ãƒ‰ã‚ãƒ¥ãƒ¡ãƒ³ãƒˆãŒè¿½ã„
labocho 2013/11/14
aws

nginx
ãƒªãƒ³ã‚¯
AWS Developer Forums: VPC Public EC2 Instance with no elastic IP cannot access YUM repos
labocho 2013/09/10
vpc eip

aws
ãƒªãƒ³ã‚¯
How to connect to outside world from amazon vpc?
I have amazon VPC set through wizard as "public only network", so all my instances are in public subnet. Instances within VPC that have Elastic IP assigned connect to internet without any troubles. But instances without elastic IP can't connect anywhere. Internet gateway is present. Route table in aws console looks like Destination Target 10.0.0.0/16 local 0.0.0.0/0 igw-nnnnn and route from inside
labocho 2013/09/10
vpc å†…ã§ eip ã‚’æŒãŸãªã„ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒå¤–ã«å‡ºã‚‹ãŸã‚ã«ã¯ nat ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ãŒå¿…è¦ã¨ã®ã“ã¨

aws
ãƒªãƒ³ã‚¯
Amazon Web Service (AWS) ã§ã‚µãƒ¼ãƒ“ã‚¹ã‚’ãƒ‡ãƒ—ãƒã‚¤ã—ã¦ã¿ãŸ | feedforce Engineers' blog
3 å¹´ã»ã©å‰ã€ ã€Œãˆã‚‚ã«ã‚…ã€ã¨ã„ã†ã‚µãƒ¼ãƒ“ã‚¹ã‚’ Amazon EC2 ã§ãƒªãƒªãƒ¼ã‚¹ã—ã¾ã—ãŸã€‚æ®‹å¿µãªãŒã‚‰ã€Œãˆã‚‚ã«ã‚…ã€ã¯ã‚µãƒ¼ãƒ“ã‚¹ã‚’çµ‚äº†ã—ã¾ã—ãŸãŒã€ä»Šå›žã€åˆ¥ãƒ—ãƒãƒ€ã‚¯ãƒˆã§å†ã³ AWS ã‚’ä½¿ã†æ©Ÿä¼šãŒã‚ã‚Šã¾ã—ãŸã€‚ã€Œãˆã‚‚ã«ã‚…ã€å½“æ™‚ã¨æ¯”ã¹ã¦ã€AWS ã‚‚å¤§ããªé€²åŒ–ã‚’é‚ã’ã¾ã—ãŸã€‚ ã€Œãˆã‚‚ã«ã‚…ã€å½“æ™‚ã«ã¯ãªã‹ã£ãŸæ±äº¬ãƒªãƒ¼ã‚¸ãƒ§ãƒ³ãŒã‚ã‚‹ã€‚ EC2 / S3 ä»¥å¤–ã«ã‚‚ VPC, ELB ã‚„ RDS ã¨ã„ã£ãŸã‚µãƒ¼ãƒ“ã‚¹ãŒå±•é–‹ã•ã‚Œã¦ã„ã‚‹ã€‚ ä¹…ã€…ã® FFTT ã§ã¯ã€ AWS ã‚’ã©ã®ã‚ˆã†ã«åˆ©ç”¨ã—ã¦ã„ã‚‹ã‹ã«ã¤ã„ã¦ã€å…¬é–‹ã§ãã‚‹ç¯„å›²ã§ã”ç´¹ä»‹ã—ãŸã„ã¨æ€ã„ã¾ã™ã€‚ AWS é¸å®šã¾ã§ã®æµã‚Œ è¦æ±‚è«¸å…ƒ ä»Šå›žã‚µãƒ¼ãƒ“ã‚¹ã‚’ç«‹ã¡ä¸Šã’ã‚‹ã«å½“ãŸã£ã¦ã€ã‚¤ãƒ³ãƒ•ãƒ©é¢ã§ã¯ä»¥ä¸‹ã®è¦æ±‚ãŒã‚ã‚Šã¾ã—ãŸã€‚ Rails 3.2 ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã‚’å‹•ä½œã•ã›ãŸã„ã€‚ IaaS ã¾ãŸã¯ãƒ‡ãƒ¼ã‚¿ã‚»ãƒ³ã‚¿ã®å ´åˆã¯ã€ä¸€èˆ¬çš„ãªãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µ â†’ Web appã‚µãƒ¼ãƒ â†’ MySQL ã¨ã„ã†æ§‹æˆã«ã—ãŸ
labocho 2013/04/11
aws
ãƒªãƒ³ã‚¯
Amazon EC2 ã§ SSH ã™ã‚‹ãªã‚‰ ec2-ssh ãŒä¾¿åˆ© - m.igrs.jp
AWSã‚’æœ¬æ ¼çš„ã«ä½¿ã„å§‹ã‚ã¦ç´„3ãƒ¶æœˆã«ãªã‚‹æ–°å‚è€…ã§ã™ã€‚ ä¾¿åˆ©éŽãŽã¦ä»Šã¾ã§ã®æ™‚é–“ã‚’è¿”ã—ã¦æ¬²ã—ã„ãã‚‰ã„ãªã®ã§ã™ãŒéŽãŽãŸã‚‚ã®ã¯ä»•æ–¹ãªã„ã®ã§å‰ã«é€²ã¿ã¾ã—ã‚‡ã†ã€‚ EC2 ã¸ã® SSH æŽ¥ç¶š Amazon EC2 ä¸Šã®ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã«SSHæŽ¥ç¶šã™ã‚‹ãƒ™ãƒ¼ã‚·ãƒƒã‚¯ãªæ–¹æ³•ã¯ ã§ã™ãŒã€ã“ã‚Œã§ã¯ä½•ã®ã‚µãƒ¼ãƒã«æŽ¥ç¶šã—ã¦ã„ã‚‹ã®ã‹ã•ã£ã±ã‚Šåˆ†ã‹ã‚‰ãªã„ã®ã§ã“ã®ã¾ã¾é‹ç”¨ã—ã¦ã„ã‚‹äººã¯ã¾ãšã„ãªã„ã§ã—ã‚‡ã†ã€‚ (AWS Management Console ã‹ã‚‰æ¯Žå›žã‚³ãƒ”ãƒšã§ãŒã‚“ã°ã£ã¦ã„ã‚‹äººã¯ã„ãã†) ~/.ssh/config ãŠãã‚‰ãå¤šãã®äººã¯ ~/.ssh/config ã®è¨å®šã«ãã‚Œãžã‚Œå·¥å¤«ã‚’å‡ã‚‰ã—ã¦ã„ã‚‹ã®ã‹ã¨æ€ã‚ã‚Œã¾ã™ãŒã€ ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹æ•°ãŒå¢—ãˆã¦ãã‚‹ã¨ ~/.ssh/config ã®æ›´æ–°ã‚‚ç…©ã‚ã—ããªã‚Šã¾ã™ã€‚ ã¾ãŸ Auto Scaling ç‰ã®ãƒ€ã‚¤ãƒŠãƒŸãƒƒã‚¯ãªé‹ç”¨ã«ãªã‚‹ã¨ã¨ã¦ã‚‚è¿½ã„ã¤ãã¾ã›ã‚“ã€‚ æ—¢å˜ã‚µãƒãƒ¼ãƒˆãƒ„ãƒ¼ãƒ« ec2ssh ãã®ç…©
labocho 2013/03/14
aws
ãƒªãƒ³ã‚¯
S3,CloudFrontã®ã‚¢ã‚¯ã‚»ã‚¹ãƒã‚°ã‚’ã¨ã‚‹ - ã™ã‚‰ã„ã‚€ãŒã‚ã‚‰ã‚ã‚ŒãŸ
S3ã‚„Cloud Frontã«ãƒ•ã‚¡ã‚¤ãƒ«ã‚’ç½®ã„ã¦é–²è¦§ã•ã›ã‚‹ã‚ˆã†ã«ã—ãŸãªã‚‰ã°ã€å½“ç„¶ã€Œã‚¢ã‚¯ã‚»ã‚¹ãƒã‚°ã¯ã©ã†ãªã‚‹ã®?!ã€ã¨èžã‹ã‚Œã‚‹ã“ã¨ã§ã—ã‚‡ã†ã€‚ ã‚‚ã¡ã‚ã‚“ã‚¢ã‚¯ã‚»ã‚¹ãƒã‚°ã‚’å–å¾—ã™ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ â– S3 ãƒã‚°ã«ã¤ã„ã¦ã®ãƒ‰ã‚ãƒ¥ãƒ¡ãƒ³ãƒˆã¯ã“ã¡ã‚‰ã€‚ Amazon Simple Storage Service Developer Guide - Server Access Logging http://docs.amazonwebservices.com/AmazonS3/latest/dev/ServerLogs.html ãƒã‚°ã®ãƒ•ã‚©ãƒ¼ãƒžãƒƒãƒˆã¯ä¸€èˆ¬çš„ãªWebã‚µãƒ¼ãƒãƒ¼ã®ãƒã‚°ã¨ã¯é•ã£ã¦ã„ã¾ã™ã€‚ Amazon Simple Storage Service Developer Guide - Server Access Log Format http://docs.amazonwebservices.com/Amaz
labocho 2012/12/09
log

aws

s3
ãƒªãƒ³ã‚¯
ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—ã®çµ‚äº†æ—¥ã‚’2020å¹´1æœˆ31æ—¥(é‡‘)ã«æ±ºå®šã—ã¾ã—ãŸ - ã¯ã¦ãªã®å‘ŠçŸ¥
ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—ã®çµ‚äº†æ—¥ã‚’2020å¹´1æœˆ31æ—¥(é‡‘)ã«æ±ºå®šã—ã¾ã—ãŸ ä»¥ä¸‹ã®ã‚¨ãƒ³ãƒˆãƒªã®é€šã‚Šã€ä»Šå¹´æœ«ã‚’ç›®å‡¦ã«ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—ã‚’çµ‚äº†äºˆå®šã§ã‚ã‚‹æ—¨ã‚’ãŠçŸ¥ã‚‰ã›ã—ã¦ãŠã‚Šã¾ã—ãŸã€‚ 2019å¹´æœ«ã‚’ç›®å‡¦ã«ã€ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—ã®æä¾›ã‚’çµ‚äº†ã™ã‚‹äºˆå®šã§ã™ - ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—æ—¥è¨˜ ã“ã®ãŸã³ã€æ£å¼ã«çµ‚äº†æ—¥ã‚’æ±ºå®šã„ãŸã—ã¾ã—ãŸã®ã§ã€ä»¥ä¸‹ã®é€šã‚Šã”ç¢ºèªãã ã•ã„ã€‚ çµ‚äº†æ—¥: 2020å¹´1æœˆ31æ—¥(é‡‘) ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆå¸Œæœ›ç”³è«‹æœŸé™:2020å¹´1æœˆ31æ—¥(é‡‘) çµ‚äº†æ—¥ä»¥é™ã¯ã€ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—ã®é–²è¦§ãŠã‚ˆã³æŠ•ç¨¿ã¯è¡Œãˆã¾ã›ã‚“ã€‚æ—¥è¨˜ã®ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆãŒå¿…è¦ãªæ–¹ã¯ä»¥ä¸‹ã®è¨˜äº‹ã«ã—ãŸãŒã£ã¦æ‰‹ç¶šãã‚’ã—ã¦ãã ã•ã„ã€‚ ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—ã«æŠ•ç¨¿ã•ã‚ŒãŸæ—¥è¨˜ãƒ‡ãƒ¼ã‚¿ã®ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆã«ã¤ã„ã¦ - ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—æ—¥è¨˜ ã”åˆ©ç”¨ã®ã¿ãªã•ã¾ã«ã¯ã”è¿·æƒ‘ã‚’ãŠã‹ã‘ã„ãŸã—ã¾ã™ãŒã€ã©ã†ãžã‚ˆã‚ã—ããŠé¡˜ã„ã„ãŸã—ã¾ã™ã€‚ 2020-06-25 è¿½è¨˜ ã¯ã¦ãªã‚°ãƒ«ãƒ¼ãƒ—æ—¥è¨˜ã®ã‚¨ã‚¯ã‚¹ãƒãƒ¼ãƒˆãƒ‡ãƒ¼ã‚¿ã¯2020å¹´2æœˆ28
labocho 2012/10/12
aws
ãƒªãƒ³ã‚¯
AWS service endpoints - AWS General Reference
To connect programmatically to an AWS service, you use an endpoint. An endpoint is the URL of the entry point for an AWS web service. The AWS SDKs and the AWS Command Line Interface (AWS CLI) automatically use the default endpoint for each service in an AWS Region. But you can specify an alternate endpoint for your API requests. If a service supports Regions, the resources in each Region are indep
labocho 2012/10/12
aws ã®ã‚¨ãƒ³ãƒ‰ãƒã‚¤ãƒ³ãƒˆä¸€è¦§

aws
ãƒªãƒ³ã‚¯
Announcement: ELB stickiness updates to support Feb 2020 Chromium CORs changes
You have been redirected here because the page you are trying to access has been archived. AWS re:Post is a cloud knowledge service launched at re:Invent 2021. We've migrated selected questions and answers from Forums to AWS re:Post. The thread you are trying to access has outdated guidance, hence we have archived it. If you would like up-to-date guidance, then share your question via AWS re:Post.
labocho 2012/07/30
elb

aws
ãƒªãƒ³ã‚¯
AWSç§»è¡Œã«å‘ã‘ãŸã‚¯ãƒƒã‚¯ãƒ‘ãƒƒãƒ‰ã®å–ã‚Šçµ„ã¿
2. â¾ƒè‡ªâ¼°å·± â€¢ oâ€¯ AWS oâ€¯ â½¤ç”¨ â½¤ç”¨ â€¢ oâ€¯ AWS â€¢â€¯ elasticfox-ec2tag IAM Fox R53 Fox oâ€¯ Ruby â€¢â€¯ zip ruby libarchive ruaâ€¦etc
labocho 2011/12/09
ã‚¯ãƒƒã‚¯ãƒ‘ãƒƒãƒ‰ã® aws æ§‹æˆ å‚è€ƒã«ãªã‚‹

aws
ãƒªãƒ³ã‚¯
http://scottpatten.ca/projects/synching-your-amazon-s3-asset-host-using-capistrano.html
labocho 2011/09/12
public ä¸‹ã‚’ s3 ã«åŒæœŸã™ã‚‹ recipe ã‚’æä¾›ã™ã‚‹ãƒ—ãƒ©ã‚°ã‚¤ãƒ³

rails

capistrano

aws
ãƒªãƒ³ã‚¯
ã‚¯ãƒ©ã‚¦ãƒ‰æ™‚ä»£ã¯DNS PinningãŒè½ã¨ã—ç©´ã«ãªã‚‹ | æ°´ç„¡æœˆã°ã‘ã‚‰ã®ãˆã³æ—¥è¨˜
å…¬é–‹: 2011å¹´9æœˆ3æ—¥19æ™‚50åˆ†é ƒ ãƒ¢ãƒãƒ„ã‚¤ (www.movatwi.jp)ã®ä½œè€…ãˆãµã—ã‚“ã•ã‚“ã¨ã€Twitterã§ã“ã‚“ãªã‚„ã‚Šã¨ã‚Šã‚’ã—ã¾ã—ãŸã€‚ Operaã£ã¦DNSã®TTLè€ƒæ…®ã—ã¦ãªã„ï¼Ÿï¼å¤šãã®ãƒ–ãƒ©ã‚¦ã‚¶ã¯å®‰å…¨æ€§ã®ãŸã‚ã«çŸã™ãŽã‚‹TTLã‚’ç„¡è¦–ã—ãŸã‚Šã—ã¾ã™ãŒ (DNS Pinning)ã€ãã‚Œã¨ã¯ã¾ãŸé•ã†è©±ã§ã—ã‚‡ã†ã‹?AWSã®Elastic Load Balancingã§ã€å‹•çš„ã«ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µãƒ¼ã®ã‚µãƒ¼ãƒãŒå¢—ãˆãŸã‚Šæ¸›ã£ãŸã‚Šã™ã‚‹ã‚ˆã†ã§ã€å¤œæ˜Žã‘ã®OperaãŒã‚ˆãå…¨ç„¶é•ã†ã‚µãƒ¼ãƒ“ã‚¹ã«ç¹‹ãŒã£ã¦ã—ã¾ã†ã“ã¨ãŒã‚ã‚‹ã‚“ã§ã™ã‚ˆãã€‚å°‘ãªãã¨ã‚‚ã‚¯ãƒƒã‚ãƒ¼ã¯é€ã£ã¡ã‚ƒã£ã¦ã¾ã™ã‚ˆã...ã‚ãƒ¼ã€ãªã‚‹ã»ã©ã€‚ãã‚Œã¯ã¾ãšã„ã§ã™ãã€‚ã“ã‚Œã¯ç›²ç‚¹ã§ã—ãŸâ€¦â€¦ã€‚ Operaã‚„IEãªã©ã¯ã€DNSã®TTLãŒçŸãè¨å®šã•ã‚Œã¦ã„ã¦ã‚‚ç„¡è¦–ã—ã¦ã‚ãƒ£ãƒƒã‚·ãƒ¥ã—ç¶šã‘ã‚‹äº‹ãŒã‚ã‚Šã¾ã™ã€‚ã“ã‚Œã¯DNSã®è² è·ã‚’æ¸›ã‚‰ã™ã¨ã„ã†ã ã‘ã¯ã§ãªãã€ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ä¸Šã®æ„å‘³ã‚‚ã‚ã‚Šã€ã€ŒDNS
labocho 2011/09/04
ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£

aws
ãƒªãƒ³ã‚¯
1