Questions tagged with AWS Management Console

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

Bug: S3 bucket static website hosting requires an index document value, even if it's just one space (when set in the management console)

The AWS S3 service allows turning on [static website hosting](https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html) on a S3 bucket. In the AWS CloudFormation [user guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-s3-websiteconfiguration.html#cfn-s3-websiteconfiguration-indexdocument), the `IndexDocument` field is specified as optional (`Required: No`). However, in the [management console](https://s3.console.aws.amazon.com/s3/), when configuring an S3 bucket for static website hosting, the "Error document" field is marked "optional", meanwhile "Index document" is not, and trying to save the changes with that field left blank doesn't work (it is highlighted with "Must be at least 1 characters long."). Making "Index document" one empty space makes it no problem. This is in line with what the [S3 user guide](https://docs.aws.amazon.com/AmazonS3/latest/userguide/IndexDocumentSupport.html) says: > When you enable website hosting, you must also configure and upload an index document. ### Steps to reproduce - View a specific S3 bucket in the [S3 management console](https://s3.console.aws.amazon.com/s3/) - In the "Properties" tab, scroll down to "Static website hosting" and click "Edit" - Under "Static website hosting", select "Enable" - Leave "Index document" blank - Click "Save changes" The "Index document" field will be highlighted in red with "Must be at least 1 characters long." - Enter one empty space in the "Index document" field - Click "Save changes" The changes will now be saved. ### Expected results "Index document" should be optional.
0
answers
0
votes
12
views
profile picture
asked a month ago

Bug: Cannot change Lambda architecture without providing a new zip file (in the management console)

AWS Lambda currently offers a choice of two CPU architectures: x86_64 and arm64. In some cases, the deployment package may not need to be changed in order to work with one architecture instead of another (it may work with either one). Also, the package might be specifically for the other architecture, and switching the architecture may not require a new package to be uploaded. However, in the management console, the new settings for a Lambda function cannot be saved after the architecture is switched if a new zip file is not also uploaded or an S3 location is provided (this occurs only if the Lambda code was previously uploaded as a zip file). ### Steps to reproduce First, either upload a zip file by clicking "Upload" under "Source code" in the [management console](https://us-east-1.console.aws.amazon.com/lambda/) or using the AWS CLI: ``` aws lambda update-function-code --function-name <function-name> --zip-file fileb://<path-to-zip-file> ``` Then: - View the Lambda function in the [management console](https://us-east-1.console.aws.amazon.com/lambda/) - Under "Runtime settings", click "Edit" - Change "Architecture" New fields appear: "Source code location" and "Code source" - Click "Save" The field "Code source" is highlighted in red: "This field is required." - Click "Upload" under "Code source" and select a zip file on the local file system **or** select "S3 location" and provide an S3 URL to the source code package under "Amazon S3 link URL" - Click "Save" The file will be uploaded and the new architecture setting with take effect. (If an S3 URL was provided, then the architecture can simply be switched on the next attempt.) ### Expected behavior The "Save" button should always work when simply selecting a different CPU architecture.
1
answers
0
votes
30
views
profile picture
asked a month ago

Unable to login via console or ssh

I see the following in the logs, the sshd service is down and cannot hit enter on console to do anything [ 0.178251] RETBleed: WARNING: Spectre v2 mitigation leaves CPU vulnerable to RETBleed attacks, data leaks possible! [ 0.957547] ena 0000:00:05.0: LLQ is not supported Fallback to host mode policy. /dev/nvme0n1p1: clean, 170121/3276800 files, 1791759/13106939 blocks [ 1.498829] systemd[1]: [/lib/systemd/system/atd.service:7] Executable path is not absolute, ignoring: -find /var/spool/cron/atjobs -type f -name "=*" -not -newercc /run/systemd -delete [ 2.585036] cloud-init[195]: Cloud-init v. 0.7.9 running 'init-local' at Wed, 26 Oct 2022 16:24:28 +0000. Up 2.53 seconds. [FAILED] Failed to start Entropy Daemon based on the HAVEGE algorithm. See 'systemctl status haveged.service' for details. [ OK ] Started Raise network interfaces. Starting Initial cloud-init job (metadata service crawler)... [ OK ] Reached target Network. [ 5.700778] cloud-init[536]: Cloud-init v. 0.7.9 running 'init' at Wed, 26 Oct 2022 16:24:31 +0000. Up 5.20 seconds. [ 5.707092] cloud-init[536]: ci-info: +++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++ [ 5.716709] cloud-init[536]: ci-info: +--------+------+---------------+---------------+-------+-------------------+ [ 5.724038] cloud-init[536]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | [ 5.816066] cloud-init[536]: ci-info: +--------+------+---------------+---------------+-------+-------------------+ [ OK ] Started Initial cloud-init job (metadata service crawler). [ 5.833254] cloud-init[536]: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | . | [ 5.916718] cloud-init[536]: ci-info: | lo: | True | . | . | d | . | [ OK ] Reached target System Initialization. [ 5.923178] cloud-init[536]: ci-info: | eth0: | True | 172.31.88.127 | 255.255.240.0 | . | 12:fa:90:47:c4:ca | [ OK ] Started Clean PHP session files every 30 mins. [ 6.020583] cloud-init[536]: ci-info: | eth0: | True | . | . | d | 12:fa:90:47:c4:ca | [ OK ] Listening on UUID daemon activation socket. [ 6.022681] cloud-init[536]: ci-info: +--------+------+---------------+---------------+-------+-------------------+ [ 6.205833] cloud-init[536]: ci-info: +++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++ [ OK ] Started Daily Cleanup of Temporary Directories. [ 6.220241] cloud-init[536]: ci-info: +-------+-------------+-------------+---------------+-----------+-------+ [ OK ] Listening on D-Bus System Message Bus Socket. [ 6.222215] cloud-init[536]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. [ 6.325642] cloud-init[536]: ci-info: +-------+-------------+-------------+---------------+-----------+-------+ [ 6.421173] cloud-init[536]: ci-info: | 0 | 0.0.0.0 | 172.31.80.1 | 0.0.0.0 | eth0 | UG | Starting vsftpd FTP server... [ OK ] Started D-Bus System Message Bus. [ 6.423014] cloud-init[536]: ci-info: | 1 | 172.31.80.0 | 0.0.0.0 | 255.255.240.0 | eth0 | U | [ 6.520804] cloud-init[536]: ci-info: +-------+-------------+-------------+---------------+-----------+-------+ Starting The Apache HTTP Server... [ OK ] Started irqbalance daemon. [ OK ] Started Deferred execution scheduler. Starting chrony, an NTP client/server... [ OK ] Started Regular background program processing daemon. Starting Login Service... [ OK ] Started Daily apt download activities. [ OK ] Started Daily apt upgrade and clean activities. [ OK ] Reached target Timers. Starting System Logging Service... [ OK ] Started Unattended Upgrades Shutdown. [ OK ] Reached target Cloud-config availability. [ OK ] Reached target Network is Online. Starting LSB: bitnami init script... Starting Apply the settings specified in cloud-config... Starting Permit User Sessions... [ 6.952653] bitnami[600]: resize2fs 1.43.4 (31-Jan-2017) [ 7.018179] bitnami[600]: open: No such file or directory while opening /dev/xvda Starting OpenBSD Secure Shell server... [ OK ] Started System Logging Service. [ OK ] Started vsftpd FTP server. [ OK ] Started The Apache HTTP Server. [ OK ] Started chrony, an NTP client/server. [ OK ] Started Permit User Sessions. [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Started Login Service. [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ 7.739533] cloud-init[601]: Cloud-init v. 0.7.9 running 'modules:config' at Wed, 26 Oct 2022 16:24:33 +0000. Up 7.52 seconds. [ OK ] Started Apply the settings specified in cloud-config. [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Stopped OpenBSD Secure Shell server. Starting OpenBSD Secure Shell server... [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ OK ] Stopped OpenBSD Secure Shell server. [FAILED] Failed to start OpenBSD Secure Shell server. See 'systemctl status ssh.service' for details. [ 10.186723] bitnami[600]: 650000+0 records in [ 10.189086] bitnami[600]: 650000+0 records out [ 10.191201] bitnami[600]: 665600000 bytes (666 MB, 635 MiB) copied, 3.19479 s, 208 MB/s [ 11.261631] bitnami[600]: Setting up swapspace version 1, size = 634.8 MiB (665595904 bytes) [ 11.265199] bitnami[600]: no label, UUID=04885367-8022-432b-99f3-3c6e5b617dbf [ 13.635358] bitnami[600]: ## 2022-10-26 16:24:39+00:00 ## INFO ## 80 has been blocked [ 15.642776] bitnami[600]: ## 2022-10-26 16:24:41+00:00 ## INFO ## 443 has been blocked [ 18.717920] bitnami[600]: /opt/bitnami/mysql/scripts/ctl.sh : mysql started at port 3306 [ 26.287353] bitnami[600]: /opt/bitnami/php/scripts/ctl.sh : php-fpm started [ 31.622222] bitnami[600]: [Wed Oct 26 16:24:57.506786 2022] [core:trace3] [pid 1145] core.c(3355): Setting LogLevel for all modules to trace8 [ 31.663500] bitnami[600]: Syntax OK [ 31.754163] bitnami[600]: [Wed Oct 26 16:24:57.638831 2022] [core:trace3] [pid 1147] core.c(3355): Setting LogLevel for all modules to trace8 [ 31.768089] bitnami[600]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80 [ 31.785974] bitnami[600]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80 [ 31.790871] bitnami[600]: no listening sockets available, shutting down [ 31.794003] bitnami[600]: AH00015: Unable to open logs [ 31.885824] bitnami[600]: /opt/bitnami/apache2/scripts/ctl.sh : httpd could not be started [ 40.254998] bitnami[600]: Starting gonit daemon [FAILED] Failed to start LSB: bitnami init script. See 'systemctl status bitnami.service' for details. [ OK ] Reached target Multi-User System. Starting Execute cloud user/final scripts... [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. [ 40.814772] cloud-init[1263]: Cloud-init v. 0.7.9 running 'modules:final' at Wed, 26 Oct 2022 16:25:06 +0000. Up 40.71 seconds. [ 40.819181] cloud-init[1263]: Cloud-init v. 0.7.9 finished at Wed, 26 Oct 2022 16:25:06 +0000. Datasource DataSourceEc2. Up 40.80 seconds [ OK ] Started Execute cloud user/final scripts. [ OK ] Reached target Cloud-init target.
0
answers
0
votes
24
views
asked a month ago